[SPARK-52293] Use super-linter for markdown files
#173
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dongjoon-hyun
commented
May 24, 2025
| # specific language governing permissions and limitations | ||
| # under the License. | ||
|
|
||
| Sources/SparkConnect/Documentation.docc/Examples.md |
There was a problem hiding this comment.
Although the file is revised cleanly, there exists a false alarm. So, we ignore this file for now in CIs.
|
Could you review this PR too, @viirya ? Thank you always! |
viirya
approved these changes
May 24, 2025
|
Thank you! Merged to main. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This PR aims to use
super-linterfor markdown files.Why are the changes needed?
For consistency.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs with the newly added
linterGitHub Action test.Was this patch authored or co-authored using generative AI tooling?
No.